Skip to content

Use oasis3-mct master branch in ACCESS-ESM1.6#311

Merged
dougiesquire merged 2 commits intomainfrom
esm1.6-oasis3-mct-master
Sep 2, 2025
Merged

Use oasis3-mct master branch in ACCESS-ESM1.6#311
dougiesquire merged 2 commits intomainfrom
esm1.6-oasis3-mct-master

Conversation

@dougiesquire
Copy link
Copy Markdown
Contributor

This PR includes changes to allow us to switch to using oasis3-mct built from the master branch, rather than access-esm1.5 branch, in ACCESS-ESM1.6.

A version("stable", branch="master", preferred=True) is introduced into the oasis3-mct SPR. Using this version in ACCESS-ESM1.6 does not change answers or performance (despite the associated change from -xCORE-AVX512 to -axCORE-AVX2) - see here and here.

Comment thread packages/oasis3-mct/package.py
@dougiesquire dougiesquire force-pushed the esm1.6-oasis3-mct-master branch from 55e86d9 to 0a82a48 Compare August 27, 2025 04:36
Comment thread packages/mom5/package.py
@dougiesquire dougiesquire force-pushed the esm1.6-oasis3-mct-master branch 2 times, most recently from cce9240 to 0ca3c0d Compare August 29, 2025 01:58
Copy link
Copy Markdown
Collaborator

@penguian penguian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What testing has been done so far?

Comment thread packages/mom5/package.py Outdated
Comment thread packages/oasis3-mct/package.py
Comment thread packages/oasis3-mct/package.py
@dougiesquire dougiesquire force-pushed the esm1.6-oasis3-mct-master branch from 0ca3c0d to 50861eb Compare September 1, 2025 02:56
@harshula
Copy link
Copy Markdown
Collaborator

harshula commented Sep 1, 2025

Hi @dougiesquire , If you haven't already, please rebase your branch on to the latest spack-packages main.

@dougiesquire
Copy link
Copy Markdown
Contributor Author

Done

@dougiesquire
Copy link
Copy Markdown
Contributor Author

@penguian, are you satisfied with my responses above? If so, could you please approve the PR?

@manodeep
Copy link
Copy Markdown
Collaborator

manodeep commented Sep 2, 2025

While I can approve, my knowledge of the ACCESS-NRI versioning scheme isn't sufficiently high to be confident. FWIW, the change seems to work fine with my local spack ESM1.6 builds for both regular oasis3-mct (which picks up access-om2) and upstream.

Copy link
Copy Markdown
Collaborator

@harshula harshula left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@penguian penguian self-requested a review September 2, 2025 02:56
@harshula
Copy link
Copy Markdown
Collaborator

harshula commented Sep 2, 2025

Hi @dougiesquire , Please use squash-merge or commit-merge, whichever you think is more appropriate.

Copy link
Copy Markdown
Collaborator

@penguian penguian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@dougiesquire dougiesquire merged commit 98bfbb2 into main Sep 2, 2025
6 checks passed
@dougiesquire dougiesquire deleted the esm1.6-oasis3-mct-master branch September 2, 2025 03:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants